-- *****************************************************************
-- CISCO-VIRTUAL-SWITCH-MIB
--
-- Definitions of managed objects supporting Virtual Switch.
--
-- Augest 2007, Frank Chao
--
-- Copyright (c) 2006-2008 by cisco Systems Inc.
-- All rights reserved.
-- *****************************************************************CISCO-VIRTUAL-SWITCH-MIB DEFINITIONS::=BEGIN
IMPORTSMODULE-IDENTITY,NOTIFICATION-TYPE,OBJECT-TYPE,Unsigned32,Counter32FROM SNMPv2-SMI
MODULE-COMPLIANCE,NOTIFICATION-GROUP,OBJECT-GROUPFROM SNMPv2-CONF
TEXTUAL-CONVENTION,RowStatus,TimeStamp,DateAndTime,TruthValueFROM SNMPv2-TC
entPhysicalIndex
FROM ENTITY-MIB
InterfaceIndexFROM IF-MIB
ciscoMgmt
FROM CISCO-SMI;ciscoVirtualSwitchMIB MODULE-IDENTITYLAST-UPDATED"200709180000Z"ORGANIZATION"Cisco Systems, Inc."
CONTACT-INFO"Cisco Systems
Customer Service
Postal: 170 W Tasman Drive
San Jose, CA 95134
Tel: +1 800 553-NETS
cs-lan-switch-snmp@cisco.com"DESCRIPTION"This MIB module defines the managed objects that support the
virtual switch architecture.
The virtual switch concept combines several individual
distributed physical switches together to build a single
logical management point. The core switches are the control
point for a virtual switch, all the traffic is forwarded and
distributed in the core switches, including control and data
traffic.
The core switches are connected through a dedicated ether
channel called Virtual Switch Link (VSL) that is used for
both control traffic as well as some data traffic to provide
the traffic load sharing and switch redundancy between the
physical chassis.
One or multiple core switches can be supported in the virtual
switch architecture, but only one core called 'active core'
switch can be active to manage the traffic. The other is
called 'standby core' switch as redundancy if there is.
The concept of virtual switch is to collect many physical
switches chassis together to form a single management unit to
simplify the whole network architecture."REVISION"200709180000Z"DESCRIPTION"Initial version of this MIB module."::={ ciscoMgmt 388}ciscoVirtualSwitchMIBNotifs OBJECTIDENTIFIER::={ ciscoVirtualSwitchMIB 0}ciscoVirtualSwitchMIBObjects OBJECTIDENTIFIER::={ ciscoVirtualSwitchMIB 1}ciscoVirtualSwitchMIBConform OBJECTIDENTIFIER::={ ciscoVirtualSwitchMIB 2}-- TEXTUAL-CONVENTIONVSSwitchID ::=TEXTUAL-CONVENTIONSTATUScurrentDESCRIPTION"An integer value that uniquely identifies a physical chassis
in the virtual switch architecture.
0 means no switch ID configured for this switch. It implies
the switch is in the standalone mode and not part of the
virtual switch architecture."SYNTAXUnsigned32VSSwitchCapability ::=TEXTUAL-CONVENTIONSTATUScurrentDESCRIPTION"Indication of the switch roles that can be supported on the
chassis device.
standalone : it means this chassis device can be a regular
switch which is not a part of virtual switch architecture.
core : it means this chassis device can be a core switch,
active or standby, in the virtual switch architecture."SYNTAXBITS{standalone(0),core(1)}VSSwitchMode ::=TEXTUAL-CONVENTIONSTATUScurrentDESCRIPTION
"The switch mode of the chassis device in the virtual
switch environment or a chassis can also be a standalone
device.
standalone : it means this chassis device is not in a part
of the virtual switch environment, it is a standalone
switch.
multiNode: it means this chassis device is in a part of
the virtual switch environment. Only a switch with the
capability to be a 'core' switch could be configured to
multiNode(2)."SYNTAXINTEGER{standalone(1),multiNode(2)}VSSwitchRole ::=TEXTUAL-CONVENTIONSTATUScurrentDESCRIPTION"The role of the chassis device.
standalone : it means this chassis device is not a part of
the virtual switch, it is a standalone switch.
active : it means this chassis device is an active core switch
in the virtual switch architecture.
standby : it means this chassis device is a standby core switch in
the virtual switch architecture."SYNTAXINTEGER{standalone(1),active(2),standby(3)}VSConnectStatus ::=TEXTUAL-CONVENTIONSTATUScurrentDESCRIPTION"A textual convention to indicate the connection status of a
link."SYNTAXINTEGER{up(1),down(2)}cvsGlobalObjects OBJECTIDENTIFIER::={ ciscoVirtualSwitchMIBObjects 1}
cvsChassisObjects OBJECTIDENTIFIER::={ ciscoVirtualSwitchMIBObjects 2}cvsVSLObjects OBJECTIDENTIFIER::={ ciscoVirtualSwitchMIBObjects 3}cvsModuleObjects OBJECTIDENTIFIER::={ ciscoVirtualSwitchMIBObjects 4}-- Virtual Switch global objectscvsDomain OBJECT-TYPESYNTAXUnsigned32MAX-ACCESSread-writeSTATUScurrentDESCRIPTION"The virtual switch domain identifier to recognize a
virtual switch domain. Only Switches with the same
domain number can be in the same virtual switch.
0 means no switch domain configured."::={ cvsGlobalObjects 1}
cvsSwitchID OBJECT-TYPESYNTAX VSSwitchID
MAX-ACCESSread-writeSTATUScurrentDESCRIPTION"The unique ID which is assigned to the current switch
for identifying this physical chassis as a core switch
in the virtual switch architecture.
0 means no switch ID configured."::={ cvsGlobalObjects 2}cvsSwitchCapability OBJECT-TYPESYNTAX VSSwitchCapability
MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The capability of the switch can be. A physical chassis can
be a standalone switch in the normal environment or a switch
which is part of the virtual switch architecture."::={ cvsGlobalObjects 3}cvsSwitchMode OBJECT-TYPESYNTAX VSSwitchMode
MAX-ACCESSread-writeSTATUScurrentDESCRIPTION"Converting a standalone switch in the regular switch
architecture to a switch in the virtual switch
architecture. Or converting a switch in the virtual
switch architecture to a standalone switch in the regular
switch architecture. And the value of this object can
only be set to one of mode where the corresponding bits in
cvsSwitchCapability is set.
To prevent vague switch status, this action will not only
change the switch mode, but also reload the device
automatically to activate to the new switch mode."::={ cvsGlobalObjects 4}cvsSwitchConvertingStatus OBJECT-TYPESYNTAXTruthValueMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"Indicating whether the switch is in the process of
converting the mode of switch which is specified in
the object cvsSwitchMode.
true(1) : the switch is in converting the switch mode.
false(2) : the switch is not in converting the switch
mode."::={ cvsGlobalObjects 5}cvsVSLChangeNotifEnable OBJECT-TYPESYNTAXTruthValueMAX-ACCESSread-writeSTATUScurrentDESCRIPTION"Enable or disable the generation of cvsVSLConnectionChangeNotif
notification."::={ cvsGlobalObjects 6}-- Virtual Switch core chassis configuration tablecvsCoreSwitchConfigTable OBJECT-TYPESYNTAXSEQUENCEOF CvsCoreSwitchConfigEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"This table describes the configuration information for
the core switches to select the active or standby
core switches in the virtual switch architecture.
If cvsDomain or cvsSwitchID objects are configured to
0, this table is not instantiated."::={ cvsChassisObjects 1}cvsCoreSwitchConfigEntry OBJECT-TYPESYNTAX CvsCoreSwitchConfigEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"An entry describes the configuration for a core switch
information in the virtual switch architecture."INDEX{ cvsCoreSwitchID }::={ cvsCoreSwitchConfigTable 1}
CvsCoreSwitchConfigEntry ::=SEQUENCE{
cvsCoreSwitchID VSSwitchID,
cvsCoreSwitchPriority Unsigned32,
cvsCoreSwitchPreempt TruthValue}cvsCoreSwitchID OBJECT-TYPESYNTAX VSSwitchID
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"The switch number as an identifier for a core switch. If the
priority value is the same, the higher switch number has the
precedence to be the active core switch."::={ cvsCoreSwitchConfigEntry 1}cvsCoreSwitchPriority OBJECT-TYPESYNTAXUnsigned32MAX-ACCESSread-writeSTATUScurrentDESCRIPTION"The configured priority information for this core switch.
This priority value will be used to choose active or standby
core switch. The core switch with the higher numerical value
will be more desirable to be chosen as an active core switch."::={ cvsCoreSwitchConfigEntry 2}cvsCoreSwitchPreempt OBJECT-TYPESYNTAXTruthValueMAX-ACCESSread-write
STATUScurrentDESCRIPTION"The configured preemption information for this core switch.
This configuration will enable or disable the preemption of
choosing the active core with higher priority."::={ cvsCoreSwitchConfigEntry 3}-- Virtual Switch chassis tablecvsChassisTable OBJECT-TYPESYNTAXSEQUENCEOF CvsChassisEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"This table describes the information of the devices listed
in the ENTITY-MIB entPhysicalTable in the virtual switch
architecture, whose entPhysicalClass is chassis(3).
This table will only be instantiated when the value of
cvsSwitchMode is 'multiNode' in the virtual switch
architecture."::={ cvsChassisObjects 2}cvsChassisEntry OBJECT-TYPE
SYNTAX CvsChassisEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"An entry describes the present chassis information in
the virtual switch architecture."INDEX{ entPhysicalIndex }::={ cvsChassisTable 1}
CvsChassisEntry ::=SEQUENCE{
cvsChassisSwitchID VSSwitchID,
cvsChassisRole VSSwitchRole,
cvsChassisUpTime TimeStamp}cvsChassisSwitchID OBJECT-TYPESYNTAX VSSwitchID
MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The unique switch ID which is assigned for identifying a
chassis in the virtual switch architecture."::={ cvsChassisEntry 1}
cvsChassisRole OBJECT-TYPESYNTAX VSSwitchRole
MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object indicates the role of this chassis in the
virtual switch architecture."::={ cvsChassisEntry 2}cvsChassisUpTime OBJECT-TYPESYNTAXTimeStampMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The time (in hundredths of a second) since the chassis
device was last re-initialized."::={ cvsChassisEntry 3}-- VSL (Virtual Switch Link) tablescvsVSLConnectionTable OBJECT-TYPESYNTAXSEQUENCEOF CvsVSLConnectionEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"This table contains the VSLs (Virtual Switch Link)
connection information of the core switches.
A bundle link is a collection of two or more physical
point-to-point links which are combined to form one
logical link. A VSL is a bundle link which spans the core
switch to connect to another core switch in the virtual
switch."::={ cvsVSLObjects 1}cvsVSLConnectionEntry OBJECT-TYPESYNTAX CvsVSLConnectionEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"The entry contains connections information of the VSL
channel interfaces between the core switches."INDEX{ cvsVSLChannelIfindex }::={ cvsVSLConnectionTable 1}
CvsVSLConnectionEntry ::=SEQUENCE{
cvsVSLChannelIfindex InterfaceIndex,
cvsVSLCoreSwitchID VSSwitchID,
cvsVSLConnectOperStatus VSConnectStatus,
cvsVSLLastConnectionStateChange DateAndTime,
cvsVSLConfiguredPortCount Unsigned32,
cvsVSLOperationalPortCount Unsigned32,
cvsVSLConnectionRowStatus RowStatus}cvsVSLChannelIfindex OBJECT-TYPESYNTAXInterfaceIndexMAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"The interface index of the VSL channel interface in the
core switch to be used for the VSL."::={ cvsVSLConnectionEntry 1}cvsVSLCoreSwitchID OBJECT-TYPESYNTAX VSSwitchID
MAX-ACCESSread-createSTATUScurrentDESCRIPTION"The switch ID will be used to form the VSL."::={ cvsVSLConnectionEntry 2}cvsVSLConnectOperStatus OBJECT-TYPESYNTAX VSConnectStatus
MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This object indicates the operational status of the VSL
connection."::={ cvsVSLConnectionEntry 3}cvsVSLLastConnectionStateChange OBJECT-TYPESYNTAXDateAndTimeMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The last time when the VSL connection was changed from
up to down or down to up."::={ cvsVSLConnectionEntry 4}
cvsVSLConfiguredPortCount OBJECT-TYPESYNTAXUnsigned32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The number of configured ports for this VSL."::={ cvsVSLConnectionEntry 5}cvsVSLOperationalPortCount OBJECT-TYPESYNTAXUnsigned32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The number of operational ports for this VSL."::={ cvsVSLConnectionEntry 6}cvsVSLConnectionRowStatus OBJECT-TYPESYNTAXRowStatusMAX-ACCESSread-createSTATUScurrent
DESCRIPTION"This object is a conceptual row entry that allows creating
or removing entries in or from the cvsVSLConnectionTable.
Creating an entry in this table means building the VSL
connection and removing an entry means to remove the VSL
connection."::={ cvsVSLConnectionEntry 7}-- VSL statistics tablecvsVSLStatsTable OBJECT-TYPESYNTAXSEQUENCEOF CvsVSLStatsEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"This table contains the VSL (Virtual Switch Link)
connection statistics information between the core switches
in the virtual switch architecture.
This table will only show the statistics information for the
channel interface in the active core switch."::={ cvsVSLObjects 2}cvsVSLStatsEntry OBJECT-TYPESYNTAX CvsVSLStatsEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"The entry contains transmitting and receiving statistics
information of the VSL channel interface in the active
core switch."INDEX{ cvsVSLChannelIfindex }::={ cvsVSLStatsTable 1}
CvsVSLStatsEntry ::=SEQUENCE{
cvsVSLTxTotalPkts Counter32,
cvsVSLTxErrorPkts Counter32,
cvsVSLTxChksumErrPkts Counter32,
cvsVSLRxTotalPkts Counter32,
cvsVSLRxErrorPkts Counter32,
cvsVSLRxChksumErrPkts Counter32}cvsVSLTxTotalPkts OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-only
STATUScurrentDESCRIPTION"The total number of transmitted packets."::={ cvsVSLStatsEntry 1}cvsVSLTxErrorPkts OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The number of transmitted error packets."::={ cvsVSLStatsEntry 2}cvsVSLTxChksumErrPkts OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The number of transmitted packets with checksum error."::={ cvsVSLStatsEntry 3}cvsVSLRxTotalPkts OBJECT-TYPE
SYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The total number of received packets."::={ cvsVSLStatsEntry 4}cvsVSLRxErrorPkts OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The number of received error packets."::={ cvsVSLStatsEntry 5}cvsVSLRxChksumErrPkts OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The number of received packets with checksum error."::={ cvsVSLStatsEntry 6}-- VSL Port statistics tablecvsVSLPortStatsTable OBJECT-TYPESYNTAXSEQUENCEOF CvsVSLPortStatsEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"This table contains the statistics information for the
configured physical ports of the VSL (Virtual Switch Link)
connection in the active core switch."::={ cvsVSLObjects 3}cvsVSLPortStatsEntry OBJECT-TYPESYNTAX CvsVSLPortStatsEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"The entry contains transmitting and receiving statistics
information for a configured physical port of the VSL
channel interface in the active core switch."INDEX{
cvsVSLChannelIfindex,
cvsVSLPortStatsIfindex
}::={ cvsVSLPortStatsTable 1}
CvsVSLPortStatsEntry ::=SEQUENCE{
cvsVSLPortStatsIfindex InterfaceIndex,
cvsVSLPortTxOkPkts Counter32,
cvsVSLPortTxFailPkts Counter32,
cvsVSLPortRxBidirPkts Counter32,
cvsVSLPortRxUnidirPkts Counter32,
cvsVSLPortRxFailPkts Counter32,
cvsVSLPortRxBadPkts Counter32}cvsVSLPortStatsIfindex OBJECT-TYPESYNTAXInterfaceIndexMAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"The interface index for the configured physical port in the
VSL."::={ cvsVSLPortStatsEntry 1}cvsVSLPortTxOkPkts OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The number of transmitted packets without errors for the port."::={ cvsVSLPortStatsEntry 2}cvsVSLPortTxFailPkts OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The number of transmitted packets that had local sending
failures, such as out of buffers and other internal errors
for the port."::={ cvsVSLPortStatsEntry 3}cvsVSLPortRxBidirPkts OBJECT-TYPESYNTAXCounter32
MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The number of received packets indicating a bidirectional link
for the port."::={ cvsVSLPortStatsEntry 4}cvsVSLPortRxUnidirPkts OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The number of received packets that do not indicate a
bidirectional link for the port."::={ cvsVSLPortStatsEntry 5}cvsVSLPortRxFailPkts OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The number of received packets with incorrect data for
the port."::={ cvsVSLPortStatsEntry 6}cvsVSLPortRxBadPkts OBJECT-TYPESYNTAXCounter32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The number of received packets with in invalid states for the
port."::={ cvsVSLPortStatsEntry 7}-- Virtual Switch module tablecvsModuleTable OBJECT-TYPESYNTAXSEQUENCEOF CvsModuleEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"This table describes the information of the physical modules
listed in the ENTITY-MIB entPhysicalTable in the virtual switch
architecture, whose entPhysicalClass is module(9). This table
only contains physical linecards, no sub-linecards or port level
module entities.
This table will only be instantiated when the value of
cvsSwitchMode is 'multiNode' in the virtual switch
architecture."::={ cvsModuleObjects 1}cvsModuleEntry OBJECT-TYPESYNTAX CvsModuleEntry
MAX-ACCESSnot-accessibleSTATUScurrentDESCRIPTION"An entry describes the present physical module information in
the virtual switch architecture."INDEX{ entPhysicalIndex }::={ cvsModuleTable 1}
CvsModuleEntry ::=SEQUENCE{
cvsModuleVSSupported TruthValue,
cvsModuleVSLCapable TruthValue,
cvsModuleSlotNumber Unsigned32}cvsModuleVSSupported OBJECT-TYPE
SYNTAXTruthValueMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The physical module is supported in the virtual switch
architecture or not."::={ cvsModuleEntry 1}cvsModuleVSLCapable OBJECT-TYPESYNTAXTruthValueMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The physical module has the capability to build the VSL
connection between 2 core switches in the virtual switch
architecture or not.
If any physical port in this physical module is with the
capability to build the VSL connection, it means this module
is VSL capable."::={ cvsModuleEntry 2}cvsModuleSlotNumber OBJECT-TYPESYNTAXUnsigned32
MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The module slot number for this physical module. If it is
in the virtual switch environment, this object returns virtual
slot number. If it is in the standalone environment, this
object returns physical slot number."::={ cvsModuleEntry 3}-- Notifications objectscvsVSLConnectionChangeNotif NOTIFICATION-TYPEOBJECTS{ cvsVSLConnectOperStatus }STATUScurrentDESCRIPTION"The notification will be generated when the state of the VSL
connection is changed."::={ ciscoVirtualSwitchMIBNotifs 1}-- ConformancecvsMIBCompliances OBJECTIDENTIFIER::={ ciscoVirtualSwitchMIBConform 1}
cvsMIBGroups OBJECTIDENTIFIER::={ ciscoVirtualSwitchMIBConform 2}-- CompliancecvsMIBCompliance MODULE-COMPLIANCESTATUScurrentDESCRIPTION"The compliance statement for entities which implement
the CISCO-VIRTUAL-SWITCH-MIB."MODULE-- this moduleMANDATORY-GROUPS{
cvsGlobalGroup,
cvsModuleGroup
}GROUP cvsCoreSwitchGroup
DESCRIPTION"This group contains the selection information of the
active or standby core switches in the virtual switch
environment. This is only mandatory for the managed
system with supporting the configuring information
of core switches."GROUP cvsChassisGroup
DESCRIPTION"This group contains physical chassis information in
the virtual switch environment. This is only
mandatory for the managed system in the virtual
switch environment."GROUP cvsVSLConnectionGroup
DESCRIPTION"This is the group to construct the VSL (Virtual
switch link) connection between core switches in the
virtual switch architecture and also provide the
information for the VSL. This is only mandatory
for the managed system with supporting the
configuration of VSL."GROUP cvsVSLStatisticsGroup
DESCRIPTION"This group contains the VSL (Virtual switch
link) statistics information in the virtual switch
environment. This is only mandatory for the managed
system in the virtual switch environment."GROUP cvsConnectionNotifsGroup
DESCRIPTION"The notifications for VSL connection status. This is
only mandatory for the managed system in the virtual
switch environment."::={ cvsMIBCompliances 1}-- Units of ConformancecvsGlobalGroup OBJECT-GROUPOBJECTS{
cvsDomain,
cvsSwitchID,
cvsSwitchCapability,
cvsSwitchMode,
cvsSwitchConvertingStatus,
cvsVSLChangeNotifEnable
}STATUScurrentDESCRIPTION"The collection of objects which are used in the
virtual switch or standalone environment."::={ cvsMIBGroups 1}cvsCoreSwitchGroup OBJECT-GROUPOBJECTS{
cvsCoreSwitchPriority,
cvsCoreSwitchPreempt
}STATUScurrentDESCRIPTION"The collection of objects which are used to configure
the selection information of the active or standby
core switches in the virtual switch environment."::={ cvsMIBGroups 2}cvsChassisGroup OBJECT-GROUPOBJECTS{
cvsChassisSwitchID,
cvsChassisRole,
cvsChassisUpTime
}STATUScurrentDESCRIPTION"The collection of objects which are used to monitor the
chassis information in virtual switch architecture."::={ cvsMIBGroups 3}cvsVSLConnectionGroup OBJECT-GROUPOBJECTS{
cvsVSLCoreSwitchID,
cvsVSLConnectOperStatus,
cvsVSLLastConnectionStateChange,
cvsVSLConfiguredPortCount,
cvsVSLOperationalPortCount,
cvsVSLConnectionRowStatus
}STATUScurrentDESCRIPTION"The collection of objects which are used to configure
the VSL connection information in standalone or virtual
switch environment."::={ cvsMIBGroups 4}cvsVSLStatisticsGroup OBJECT-GROUPOBJECTS{
cvsVSLTxTotalPkts,
cvsVSLTxErrorPkts,
cvsVSLTxChksumErrPkts,
cvsVSLRxTotalPkts,
cvsVSLRxErrorPkts,
cvsVSLRxChksumErrPkts,
cvsVSLPortTxOkPkts,
cvsVSLPortTxFailPkts,
cvsVSLPortRxBidirPkts,
cvsVSLPortRxUnidirPkts,
cvsVSLPortRxFailPkts,
cvsVSLPortRxBadPkts
}
STATUScurrentDESCRIPTION"The collection of objects which are used to monitor
the VSL statistics information in virtual switch
architecture."::={ cvsMIBGroups 5}cvsModuleGroup OBJECT-GROUPOBJECTS{
cvsModuleVSSupported,
cvsModuleVSLCapable,
cvsModuleSlotNumber
}STATUScurrentDESCRIPTION"The collection of objects which are used to monitor the
physical module information."::={ cvsMIBGroups 6}cvsConnectionNotifsGroup NOTIFICATION-GROUPNOTIFICATIONS{ cvsVSLConnectionChangeNotif }STATUScurrentDESCRIPTION"The collection of notifications for the connections in
virtual switch environment."::={ cvsMIBGroups 7}END